<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html lang="en">
<head>
<meta name="copyright" content="Copyright (c) IBM Corporation and others 2011, 2013. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<meta http-equiv="Content-Style-Type" content="text/css">
<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
<title>Adopting 4.3 mechanisms and APIs</title>
</head>

<body>

<h1>Adopting 4.3 mechanisms and APIs</h1>

<p>
  This section describes changes that are required if you are trying to change 
  your 4.2 plug-in to adopt the 4.3 mechanisms and APIs.
</p>

<ol>
  <li><a href="#2x-manifest">Ensure all plug-ins include an OSGi manifest</a></li>
</ol>

<hr>
<!-- ############################################## -->
<h2>1. <a name="2x-manifest">Ensure all plug-ins include an OSGi manifest</a></h2>
<p>
The Eclipse platform 4.3 release is the <b>final</b> release that will support
2.x style Eclipse plug-ins with no OSGi manifest file (MANIFEST.MF). A warning
will now be logged when such plug-ins are encountered, with a log entry like this:
</p>
<pre>
The plugin &quot;com.acme.ancient.plugin&quot; with the version &quot;1.0.1&quot; is an old style Eclipse 2.0 
plugin with no OSGi bundle manifest. Support for Eclipse 2.0 style plugins will be removed in a future release.
</pre>
<p>
If you see such a log entry for your plug-in, you must migrate now. Migrate
by clicking the link in the plug-in manifest editor entitled, &quot;create an OSGi bundle manifest.&quot;
For more details see <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=407312">bug 407312</a>.
</p>


<!-- ############################################## -->
</body>
</html>
